OpenEdge Getting Started:<br />New and Revised Features OpenEdge Adapter for SonicMQ

Release 10.1A includes several enhancements to the OpenEdge® Adapter for SonicMQ®.

New OpenEdge Adapter for SonicMQ architecture

Release 10.1A includes two new adapter models for 4GL applications to access SonicMQ functionality:

OpenEdge Adapter for SonicMQ ClientConnect (ClientConnect) — ClientConnect runs as a process started and managed by OpenEdge clients directly when an application requires messaging.

OpenEdge Adapter for SonicMQ ServerConnect (ServerConnect) — ServerConnect runs a single adapter process per ubroker process, allowing multiple server processes to connect to this single adapter process.

Note: The existing connection model is now known as OpenEdge Adapter for SonicMQ BrokerConnect (BrokerConnect).

Unified domain support (JMS 1.1)

Prior to OpenEdge Release 10.1, clients were required to create a JMS session for either PTP or Pub/Sub. In OpenEdge Release 10.1, clients can use both PTP and Pub/Sub in the same JMS session by using the unified domain model, jmssession.p.

Client persistence

Client persistence allows the JMS session to continue sending messages regardless of the SonicMQ Broker status. If the SonicMQ Broker is not available, the messages are stored locally and sent when the SonicMQ Broker becomes available. New APIs to support this feature include the createRejectedMessageConsumer procedure, the setCientPersistence procedure, the getClientPersistence function, the setLocalStoreDirectory procedure, the getLocalStoreDirectory function, the setLocalStoreSize procedure, the getLocalStoreSize function, the setReconnectTimeout procedure, the getReconnectTimeout function, the setReconnectInterval procedure, the getReconnectInterval function, the setLocalStoreWait procedure, and the getLocalStoreWait function.

Client persistence is only available to 4GL clients who use the new ClientConnect or ServerConnect functionality.

Fault tolerance

Fault-tolerant connections allow another SonicMQ Broker to take over if the original SonicMQ Broker fails. To ensure message delivery, use the fault-tolerant APIs to set up and enable fault tolerance. New APIs to support this feature include the setFaultTolerant procedure, the getFaultTolerant function, the isFaultTolerant function, the setFaultTolerantReconnectTimeout procedure, the getFaultTolerantReconnectTimeout function, the setInitialConnectionTimeout procedure, the getInitialConnectionTimeout function, the setClientTransactionBufferSize procedure, the getClientTransactionBufferSize function, and the createChangeStateConsumer procedure.

Fault tolerance is only available to 4GL clients who use the new ClientConnect or ServerConnect functionality.

Temporary queues and topics

A temporary queue or topic allows an application to create and delete temporary queues or topics on the current connection to the SonicMQ Broker. A temporary queue or topic allows the SonicMQ Broker to hold JMS messages during the JMS session. A temporary queue or topic can be used in 4GL client code or can be used by 4GL code running in an AppServer. New APIs to support this feature include the createTemporaryQueue procedure, the deleteTemporaryQueue procedure, the createTemporaryTopic procedure, and the deleteTemporaryTopic procedure.

Server-based message selectors

SonicMQ messages can be filtered so that only messages meeting a specific criteria will be received. Message selectors filter messages so a client does not receive all the messages. Server-based message selectors are available with all adapters models. New APIs to support this feature include the setSelectorAtBroker procedure and the getSelectorAtBroker function.

Serialized connection objects

A serialized connection object contains all the connection information required by a client to connect to a SonicMQ Broker. A SonicMQ administrator creates the serialized connection object as a file using the Sonic Management Console and provides the serialized connection object to the 4GL client. The new API to support this feature is the setConnectionFile procedure.

Enhanced XML support

Release 10.1A includes additional support for the SonicMQ message type of XMLMessage. The 4GL client can send more types of data as XMLMessages including temp-tables, ProDataSets, SAX-READER, SAX-WRITER, and X-DOCUMENT. New APIs to support this feature include the createDataSetMessage procedure, the setDataSet procedure, the getDataSet function, the createTempTableMessage procedure, the setTempTable procedure, the getTempTable function, the createXMLMessage procedure, getSaxWriter function, the deleteSaxWriter procedure, the setSaxReader procedure, the setX-Document procedure, and the getX-Document function.